A good option is what Sava and Ljuba suggested about creating a
Standings section and individual articles per club.
Then, in template (let's say you create soccer_standings.tpl) you
write code like this:
Club Name
Points
{{ list_articles constraints="type is soccer_club" order="bysectionorder" }}
{{ $campsite->soccer_club->name }}
{{ $campsite->soccer_club->points }}
{{ /list_articles }}
In this example "soccer_club" is an article type with relevant fields,
you can create as many as you need to save standing table.
Notice ordering here has to be made by hand. You go to articles list
(a.k.a. clubs) in section Standings and use the "Order" column to set
order as it should be.
Then, sentence order="bysectionorder" you can see in the code above
will list clubs following that handy order you gave to the list.
This way, after every week game you must edit articles to update the
points field. Besides, you must set the ordering in the articles list
to reflect the actual standings table.
A more auto approach for the ordering should be possible, but this is
my 2 cents so far
Cheers,
On Wed, Jan 13, 2010 at 3:43 PM, wrote:
> Author: Terix
> Link:
Yes i'm implementing in this way, even if my staff is not jumping in happiness... how much is complex to write a plug-in? I didn't find documentation on how to write a plug-in from scratch.